Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle potentially abuse eval lengths #69

Merged
merged 1 commit into from
Oct 6, 2024
Merged

Handle potentially abuse eval lengths #69

merged 1 commit into from
Oct 6, 2024

Conversation

AbstractUmbra
Copy link
Collaborator

Description

See title.

Checklist

  • If code changes were made then they have been tested.
    • I have updated the documentation to reflect the changes.
    • I have updated the changelog with a quick recap of my changes.
  • This PR fixes an issue.
  • This PR adds something new (e.g. new method or parameters).
  • This PR is a breaking change (e.g. methods or parameters removed/renamed)
  • This PR is not a code change (e.g. documentation, README, ...)
  • I have read and agree to the Developer Certificate of Origin for this contribution

@AbstractUmbra AbstractUmbra self-assigned this Oct 6, 2024
chillymosh
chillymosh approved these changes Oct 6, 2024
View reviewed changes
Copy link
Contributor

@chillymosh chillymosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AbstractUmbra AbstractUmbra merged commit fc313aa into main Oct 6, 2024
3 checks passed
@AbstractUmbra AbstractUmbra deleted the fix/eval-output-length branch October 6, 2024 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@chillymosh chillymosh chillymosh approved these changes

@EvieePy EvieePy Awaiting requested review from EvieePy

Assignees

@AbstractUmbra AbstractUmbra

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@AbstractUmbra @chillymosh